Mobile assisted enhancements to reduce radio resource control (RRC) signaling

ABSTRACT

Techniques discussed herein can reduce RRC signaling messages, and various aspects can employ one or more of these sets of techniques. A first set of techniques can be employed to reduce RACH (Random Access Channel) requests from an RRC Idle State SIM (Subscriber Identity Module) of a UE in DSDS (Dual SIM Dual Standby) mode. A second set of techniques can be employed to reduce the number of RACH attempts to obtain NotBroadcasted (e.g., On Demand) SI(s) (System Information(s)) by a UE in response to a page message indicating SI modification.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 63/017,181 filed Apr. 29, 2020, entitled “MOBILEASSISTED ENHANCEMENTS TO REDUCE RADIO RESOURCE CONTROL (RRC) SIGNALING”,the contents of which are herein incorporated by reference in theirentirety.

BACKGROUND

Mobile communication in the next generation wireless communicationsystem, 5G, or new radio (NR) network will provide ubiquitousconnectivity and access to information, as well as ability to sharedata, around the globe. 5G networks and network slicing will be aunified, service-based framework that will target to meet versatile andsometimes, conflicting performance criteria and provide services tovastly heterogeneous application domains ranging from Enhanced MobileBroadband (eMBB) to massive Machine-Type Communications (mMTC),Ultra-Reliable Low-Latency Communications (URLLC), and othercommunications. In general, NR will evolve based on third generationpartnership project (3GPP) long term evolution (LTE)-Advanced technologywith additional enhanced radio access technologies (RATs) to enableseamless and faster wireless connectivity solutions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an architecture of a systemincluding a Core Network (CN), for example a Fifth Generation (5G) CN(5GC), in accordance with various aspects.

FIG. 2 is a diagram illustrating example components of a device that canbe employed in accordance with various aspects discussed herein.

FIG. 3 is a diagram illustrating example interfaces of basebandcircuitry that can be employed in accordance with various aspectsdiscussed herein.

FIG. 4 is a block diagram illustrating a system that facilitatesreducing Radio Resource Control (RRC) signaling from a UE in a varietyof scenarios, according to various aspects discussed herein.

FIG. 5 is a flow diagram of an example method or process employable at aUE that facilitates reducing RACH requests from a first SIM without anestablished RRC connection of a UE in DSDS mode, according to variousaspects discussed herein.

FIG. 6 is a flow diagram of an example method or process employable at aUE that facilitates reducing RACH requests to obtain On Demand SI(s) inresponse to a page for SI modification, according to various aspectsdiscussed herein.

DETAILED DESCRIPTION

The present disclosure will now be described with reference to theattached drawing figures, wherein like reference numerals are used torefer to like elements throughout, and wherein the illustratedstructures and devices are not necessarily drawn to scale. As utilizedherein, terms “component,” “system,” “interface,” and the like areintended to refer to a computer-related entity, hardware, software(e.g., in execution), and/or firmware. For example, a component can be aprocessor (e.g., a microprocessor, a controller, or other processingdevice), a process running on a processor, a controller, an object, anexecutable, a program, a storage device, a computer, a tablet PC and/ora user equipment (e.g., mobile phone or other device configured tocommunicate via a 3GPP RAN, etc.) with a processing device. By way ofillustration, an application running on a server and the server can alsobe a component. One or more components can reside within a process, anda component can be localized on one computer and/or distributed betweentwo or more computers. A set of elements or a set of other componentscan be described herein, in which the term “set” can be interpreted as“one or more,” unless the context indicates otherwise (e.g., “the emptyset,” “a set of two or more Xs,” etc.).

Further, these components can execute from various computer readablestorage media having various data structures stored thereon such as witha module, for example. The components can communicate via local and/orremote processes such as in accordance with a signal having one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across anetwork, such as, the Internet, a local area network, a wide areanetwork, or similar network with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, in which the electric or electronic circuitry canbe operated by a software application or a firmware application executedby one or more processors. The one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components.

Use of the word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform. Furthermore, to the extent that the terms “including”, “includes”,“having”, “has”, “with”, or variants thereof are used in either thedetailed description and the claims, such terms are intended to beinclusive in a manner similar to the term “comprising.” Additionally, insituations wherein one or more numbered items are discussed (e.g., a“first X”, a “second X”, etc.), in general the one or more numbereditems can be distinct or they can be the same, although in somesituations the context may indicate that they are distinct or that theyare the same.

As used herein, the term “circuitry” can refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someaspects, the circuitry can be implemented in, or functions associatedwith the circuitry can be implemented by, one or more software orfirmware modules. In some aspects, circuitry can include logic, at leastpartially operable in hardware.

Various aspects discussed herein can relate to facilitating wirelesscommunication, and the nature of these communications can vary.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Aspects described herein can be implemented into a system using anysuitably configured hardware and/or software. FIG. 1 illustrates anarchitecture of a system 100 including a Core Network (CN) 120, forexample a Fifth Generation (5G) CN (5GC), in accordance with variousaspects. The system 100 is shown to include a UE 101, which can be thesame or similar to one or more other UEs discussed herein; a ThirdGeneration Partnership Project (3GPP) Radio Access Network (Radio AN orRAN) or other (e.g., non-3GPP) AN, (R)AN 210, which can include one ormore RAN nodes (e.g., Evolved Node B(s) (eNB(s)), next generation NodeB(s) (gNB(s), and/or other nodes) or other nodes or access points; and aData Network (DN) 203, which can be, for example, operator services,Internet access or third party services; and a Fifth Generation CoreNetwork (5GC) 120. The 5GC 120 can comprise one or more of the followingfunctions and network components: an Authentication Server Function(AUSF) 122; an Access and Mobility Management Function (AMF) 121; aSession Management Function (SMF) 124; a Network Exposure Function (NEF)123; a Policy Control Function (PCF) 126; a Network Repository Function(NRF) 125; a Unified Data Management (UDM) 127; an Application Function(AF) 128; a User Plane (UP) Function (UPF) 102; and a Network SliceSelection Function (NSSF) 129, which can be connected by variousinterfaces and/or reference points, for example, as shown in FIG. 1 .

FIG. 2 illustrates example components of a device 200 in accordance withsome aspects. In some aspects, the device 200 can include applicationcircuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry206, front-end module (FEM) circuitry 208, one or more antennas 210, andpower management circuitry (PMC) 212 coupled together at least as shown.The components of the illustrated device 200 can be included in a UE ora RAN node. In some aspects, the device 200 can include fewer elements(e.g., a RAN node may not utilize application circuitry 202, and insteadinclude a processor/controller to process IP data received from a CNsuch as 5GC 120 or an Evolved Packet Core (EPC)). In some aspects, thedevice 200 can include additional elements such as, for example,memory/storage, display, camera, sensor, or input/output (I/O)interface. In other aspects, the components described below can beincluded in more than one device (e.g., said circuitries can beseparately included in more than one device for Cloud-RAN (C-RAN)implementations).

The application circuitry 202 can include one or more applicationprocessors. For example, the application circuitry 202 can includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) can include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors can be coupledwith or can include memory/storage and can be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 200. In some aspects,processors of application circuitry 202 can process IP data packetsreceived from an EPC.

The baseband circuitry 204 can include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 204 can include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 206 and to generate baseband signals for atransmit signal path of the RF circuitry 206. Baseband processingcircuitry 204 can interface with the application circuitry 202 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 206. For example, in some aspects, thebaseband circuitry 204 can include a third generation (3G) basebandprocessor 204A, a fourth generation (4G) baseband processor 204B, afifth generation (5G) baseband processor 204C, or other basebandprocessor(s) 204D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 204 (e.g.,one or more of baseband processors 204A-D) can handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 206. In other aspects, some or all of thefunctionality of baseband processors 204A-D can be included in modulesstored in the memory 204G and executed via a Central Processing Unit(CPU) 204E. The radio control functions can include, but are not limitedto, signal modulation/demodulation, encoding/decoding, radio frequencyshifting, etc. In some aspects, modulation/demodulation circuitry of thebaseband circuitry 204 can include Fast-Fourier Transform (FFT),precoding, or constellation mapping/demapping functionality. In someaspects, encoding/decoding circuitry of the baseband circuitry 204 caninclude convolution, tail-biting convolution, turbo, Viterbi, or LowDensity Parity Check (LDPC) encoder/decoder functionality. Aspects ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and can include other suitable functionalityin other aspects.

In some aspects, the baseband circuitry 204 can include one or moreaudio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F caninclude elements for compression/decompression and echo cancellation andcan include other suitable processing elements in other aspects.Components of the baseband circuitry can be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome aspects. In some aspects, some or all of the constituent componentsof the baseband circuitry 204 and the application circuitry 202 can beimplemented together such as, for example, on a system on a chip (SOC).

In some aspects, the baseband circuitry 204 can provide forcommunication compatible with one or more radio technologies. Forexample, in some aspects, the baseband circuitry 204 can supportcommunication with a NG-RAN, an evolved universal terrestrial radioaccess network (EUTRAN) or other wireless metropolitan area networks(WMAN), a wireless local area network (WLAN), a wireless personal areanetwork (WPAN), etc. Aspects in which the baseband circuitry 204 isconfigured to support radio communications of more than one wirelessprotocol can be referred to as multi-mode baseband circuitry.

RF circuitry 206 can enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious aspects, the RF circuitry 206 can include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 206 can include a receive signal path which caninclude circuitry to down-convert RF signals received from the FEMcircuitry 208 and provide baseband signals to the baseband circuitry204. RF circuitry 206 can also include a transmit signal path which caninclude circuitry to up-convert baseband signals provided by thebaseband circuitry 204 and provide RF output signals to the FEMcircuitry 208 for transmission.

In some aspects, the receive signal path of the RF circuitry 206 caninclude mixer circuitry 206 a, amplifier circuitry 206 b and filtercircuitry 206 c. In some aspects, the transmit signal path of the RFcircuitry 206 can include filter circuitry 206 c and mixer circuitry 206a. RF circuitry 206 can also include synthesizer circuitry 206 d forsynthesizing a frequency for use by the mixer circuitry 206 a of thereceive signal path and the transmit signal path. In some aspects, themixer circuitry 206 a of the receive signal path can be configured todown-convert RF signals received from the FEM circuitry 208 based on thesynthesized frequency provided by synthesizer circuitry 206 d. Theamplifier circuitry 206 b can be configured to amplify thedown-converted signals and the filter circuitry 206 c can be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals can be provided to the basebandcircuitry 204 for further processing. In some aspects, the outputbaseband signals can be zero-frequency baseband signals, although thisis not a requirement. In some aspects, mixer circuitry 206 a of thereceive signal path can comprise passive mixers, although the scope ofthe aspects is not limited in this respect.

In some aspects, the mixer circuitry 206 a of the transmit signal pathcan be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 206 d togenerate RF output signals for the FEM circuitry 208. The basebandsignals can be provided by the baseband circuitry 204 and can befiltered by filter circuitry 206 c.

In some aspects, the mixer circuitry 206 a of the receive signal pathand the mixer circuitry 206 a of the transmit signal path can includetwo or more mixers and can be arranged for quadrature downconversion andupconversion, respectively. In some aspects, the mixer circuitry 206 aof the receive signal path and the mixer circuitry 206 a of the transmitsignal path can include two or more mixers and can be arranged for imagerejection (e.g., Hartley image rejection). In some aspects, the mixercircuitry 206 a of the receive signal path and the mixer circuitry 206 acan be arranged for direct downconversion and direct upconversion,respectively. In some aspects, the mixer circuitry 206 a of the receivesignal path and the mixer circuitry 206 a of the transmit signal pathcan be configured for super-heterodyne operation.

In some aspects, the output baseband signals and the input basebandsignals can be analog baseband signals, although the scope of theaspects is not limited in this respect. In some alternate aspects, theoutput baseband signals and the input baseband signals can be digitalbaseband signals. In these alternate aspects, the RF circuitry 206 caninclude analog-to-digital converter (ADC) and digital-to-analogconverter (DAC) circuitry and the baseband circuitry 204 can include adigital baseband interface to communicate with the RF circuitry 206.

In some dual-mode aspects, a separate radio IC circuitry can be providedfor processing signals for each spectrum, although the scope of theaspects is not limited in this respect.

In some aspects, the synthesizer circuitry 206 d can be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theaspects is not limited in this respect as other types of frequencysynthesizers can be suitable. For example, synthesizer circuitry 206 dcan be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 206 d can be configured to synthesize anoutput frequency for use by the mixer circuitry 206 a of the RFcircuitry 206 based on a frequency input and a divider control input. Insome aspects, the synthesizer circuitry 206 d can be a fractional N/N+1synthesizer.

In some aspects, frequency input can be provided by a voltage controlledoscillator (VCO), although that is not a requirement. Divider controlinput can be provided by either the baseband circuitry 204 or theapplications processor 202 depending on the desired output frequency. Insome aspects, a divider control input (e.g., N) can be determined from alook-up table based on a channel indicated by the applications processor202.

Synthesizer circuitry 206 d of the RF circuitry 206 can include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some aspects, the divider can be a dual modulus divider(DMD) and the phase accumulator can be a digital phase accumulator(DPA). In some aspects, the DMD can be configured to divide the inputsignal by either N or N+1 (e.g., based on a carry out) to provide afractional division ratio. In some example aspects, the DLL can includea set of cascaded, tunable, delay elements, a phase detector, a chargepump and a D-type flip-flop. In these aspects, the delay elements can beconfigured to break a VCO period up into Nd equal packets of phase,where Nd is the number of delay elements in the delay line. In this way,the DLL provides negative feedback to help ensure that the total delaythrough the delay line is one VCO cycle.

In some aspects, synthesizer circuitry 206 d can be configured togenerate a carrier frequency as the output frequency, while in otheraspects, the output frequency can be a multiple of the carrier frequency(e.g., twice the carrier frequency, four times the carrier frequency)and used in conjunction with quadrature generator and divider circuitryto generate multiple signals at the carrier frequency with multipledifferent phases with respect to each other. In some aspects, the outputfrequency can be a LO frequency (fLO). In some aspects, the RF circuitry206 can include an IQ/polar converter.

FEM circuitry 208 can include a receive signal path which can includecircuitry configured to operate on RF signals received from one or moreantennas 210, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 206 for furtherprocessing. FEM circuitry 208 can also include a transmit signal pathwhich can include circuitry configured to amplify signals fortransmission provided by the RF circuitry 206 for transmission by one ormore of the one or more antennas 210. In various aspects, theamplification through the transmit or receive signal paths can be donesolely in the RF circuitry 206, solely in the FEM 208, or in both the RFcircuitry 206 and the FEM 208.

In some aspects, the FEM circuitry 208 can include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry can include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry can include an LNA toamplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 206). The transmitsignal path of the FEM circuitry 208 can include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 206), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 210).

In some aspects, the PMC 212 can manage power provided to the basebandcircuitry 204. In particular, the PMC 212 can control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMC 212 can often be included when the device 200 is capable ofbeing powered by a battery, for example, when the device is included ina UE. The PMC 212 can increase the power conversion efficiency whileproviding desirable implementation size and heat dissipationcharacteristics.

While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry204. However, in other aspects, the PMC 212 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to,application circuitry 202, RF circuitry 206, or FEM 208.

In some aspects, the PMC 212 can control, or otherwise be part of,various power saving mechanisms of the device 200. For example, if thedevice 200 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it can entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 200 can power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 200 can transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 200 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 200may not receive data in this state; in order to receive data, it cantransition back to RRC_Connected state.

An additional power saving mode can allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and can power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 202 and processors of thebaseband circuitry 204 can be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 204, alone or in combination, can be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 204 can utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 can comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 can comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1can comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 3 illustrates example interfaces of baseband circuitry inaccordance with some aspects. As discussed above, the baseband circuitry204 of FIG. 2 can comprise processors 204A-204E and a memory 204Gutilized by said processors. Each of the processors 204A-204E caninclude a memory interface, 304A-304E, respectively, to send/receivedata to/from the memory 204G.

The baseband circuitry 204 can further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 312 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 204), an application circuitryinterface 314 (e.g., an interface to send/receive data to/from theapplication circuitry 202 of FIG. 2 ), an RF circuitry interface 316(e.g., an interface to send/receive data to/from RF circuitry 206 ofFIG. 2 ), a wireless hardware connectivity interface 318 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 320 (e.g., an interface to send/receive power or controlsignals to/from the PMC 212).

In various aspects, one or more baseband processor(s) 204A-204E can alsointerface with one or more Subscriber Identity Modules (SIMs) (e.g.,which can include Universal SIMs (USIMs), etc.) 324 (which are not partof baseband circuitry 204, and can be configured to be removable from aUE such as device 200) via a UICC (UMTS (Universal Mobile TelephonySystem) Integrated Circuit Card)/Terminal interface 322 or similarinterface. Depending on the aspects and applications, a UE can compriseone SIM or more than one SIM (e.g., at least two SIMs to be capable ofoperation in a Dual SIM Dual Standby or Dual Active mode, etc.), each ofwhich can be associated with a unique International Mobile SubscriberIdentity (IMSI) which can facilitate operation on one or more 3GPPnetworks.

As discussed in greater detail herein, various aspects, which can beemployed, for example, at a UE, can facilitate a reduction in certaintypes of Radio Resource Control (RRC) signaling messages. Two differentsets of techniques are discussed herein that can reduce RRC signalingmessages, and various aspects can employ one or more of these sets oftechniques. A first set of techniques can be employed to reduce RACH(Random Access Channel) requests from an RRC Idle State SIM (SubscriberIdentity Module) of a UE in DSDS (Dual SIM Dual Standby) mode, whereinboth SIMs can be employed through time-based multiplexing, with at mostone SIM active at a time (e.g., wherein the SIMs are associated with thesame and/or overlapping transceiver architecture(s)). A second set oftechniques can be employed to reduce the number of RACH attempts toobtain NotBroadcasted SI(s) (System Information(s)) by a UE in responseto a page message indicating SI modification.

Referring to FIG. 4 , illustrated is a block diagram of a system 400employable at a UE (User Equipment), a next generation Node B (gNodeB orgNB) or other BS (base station)/TRP (Transmit/Receive Point), or anothercomponent of a 3GPP (Third Generation Partnership Project) network(e.g., a 5GC (Fifth Generation Core Network)) component or function suchas a UPF (User Plane Function)) that facilitates reducing Radio ResourceControl (RRC) signaling from the UE in a variety of scenarios, accordingto various aspects discussed herein. System 400 can include processor(s)410, communication circuitry 420, and memory 430. Processor(s) 410(e.g., which can comprise one or more of 202 and/or 204A-204F, etc.) cancomprise processing circuitry and associated interface(s) (e.g., acommunication interface (e.g., RF circuitry interface 316) forcommunicating with communication circuitry 420, a memory interface(e.g., memory interface 312) for communicating with memory 430, etc.).Communication circuitry 420 can comprise, for example circuitry forwired and/or wireless connection(s) (e.g., 206 and/or 208), which caninclude transmitter circuitry (e.g., associated with one or moretransmit chains) and/or receiver circuitry (e.g., associated with one ormore receive chains), wherein transmitter circuitry and receivercircuitry can employ common and/or distinct circuit elements, or acombination thereof). Memory 430 can comprise one or more memory devices(e.g., memory 204G, local memory (e.g., including CPU register(s)) ofprocessor(s) discussed herein, etc.) which can be of any of a variety ofstorage mediums (e.g., volatile and/or non-volatile according to any ofa variety of technologies/constructions, etc.), and can storeinstructions and/or data associated with one or more of processor(s) 410or transceiver circuitry 420).

Specific types of aspects of system 400 (e.g., UE aspects) can beindicated via subscripts (e.g., system 400 _(UE) comprising processor(s)410 _(UE), communication circuitry 420 _(UE), and memory 430 _(UE)). Insome aspects, such as BS aspects (e.g., system 400 _(gNB)) and networkcomponent (e.g., UPF (User Plane Function), etc.) aspects (e.g., system400 _(UPF)) processor(s) 410 _(gNB) (etc.), communication circuitry(e.g., 420 _(gNB), etc.), and memory (e.g., 430 _(gNB), etc.) can be ina single device or can be included in different devices, such as part ofa distributed architecture. In aspects, signaling or messaging betweendifferent aspects of system 400 (e.g., 400 ₁ and 400 ₂) can be generatedby processor(s) 410 ₁, transmitted by communication circuitry 420 ₁ overa suitable interface or reference point (e.g., a 3GPP air interface, N3,N4, etc.), received by communication circuitry 420 ₂, and processed byprocessor(s) 410 ₂. Depending on the type of interface, additionalcomponents (e.g., antenna(s), network port(s), etc. associated withsystem(s) 400 ₁ and 400 ₂) can be involved in this communication.

In various aspects, one or more of information (e.g., systeminformation, resources associated with signaling, etc.), features,parameters, etc. can be configured to a UE via signaling (e.g.,associated with one or more layers, such as L1 signaling or higher layersignaling (e.g., MAC, RRC, etc.)) from a gNB or other access point(e.g., via signaling generated by processor(s) 410 _(gNB), transmittedby communication circuitry 420 _(gNB), received by communicationcircuitry 420 _(UE), and processed by processor(s) 410 _(UE)). Dependingon the type of information, features, parameters, etc., the type ofsignaling employed and/or the exact details of the operations performedat the UE and/or gNB in processing (e.g., signaling structure, handlingof PDU(s)/SDU(s), etc.) can vary. However, for convenience, suchoperations can be referred to herein as configuringinformation/feature(s)/parameter(s)/etc. to a UE, generating orprocessing configuration signaling, or via similar terminology.

In 3GPP (Third Generation Partnership Project) systems, a UE can sendRRC messages in the following scenarios. Various aspects can reduce(e.g., minimize or eliminate) RRC signaling via techniques discussedherein.

In a first scenario, when a UE is in DSDS (Dual SIM Dual Standby) modeand both SIMs belong to the same carrier (e.g., NW operator), in variousaspects, an RRC Connected/Inactive state subscription for one of theSIMs can be used to help fetch the NotBroadcasted SIs for the other SIMwhen in RRC Idle state via a first set of techniques described herein,which can reduce RACH requests for the Idle state SIM.

In a second scenario, when a UE receives a page message indicating SI(System Information) modification wherein one or more NotBroadcasted(e.g., On Demand) SIs have changed, a second set of techniques discussedherein can be employed to reduce the number of RACH attempts to obtainthe NotBroadcasted SI(s).

Reducing RACH Requests for an RRC Idle State SIM of a UE in DSDS Mode

A first set of techniques can reduce RACH requests for a first SIM(SIM1) without an established RRC connection (e.g., in an RRC Idle stateor in an acquisition (ACQ) procedure) of a UE in DSDS mode wherein asecond SIM (SIM2) of the UE is associated with the same carrier as thefirst SIM (e.g., and has an established RRC connection). Various aspectscan employ the first set of techniques to obtain one or more On DemandSIs for the first SIM via the second SIM.

Depending on the RRC state of the second SIM, the first set oftechniques can be employed in any of a variety of scenarios wherein theUE is in DSDS mode, both the first and second SIMs belong to the samecarrier, and SIM1 is either in RRC Idle state or in the middle of an ACQprocedure. Depending on the RRC state of SIM2, a UE can obtain On DemandSI(s) for SIM1 via SIM2 as discussed in the following scenarios.

In some scenarios, SIM2 can be in an RRC inactive state. Depending onthe specific scenario, SIM1 can be in RRC idle state and determining theOn Demand SI(s) to be requested or SIM1 can be in the middle of an ACQprocedure wherein SIM would figure out the On Demand SI(s) to berequested. In either type of scenario, if SIM2 is about to initiate anRRC Resume procedure for Mobile Originated (MO)-Data and the MO-Data isnot of high priority then, SIM2 can buffer the initiated RRC resumeprocedure, such that once SIM1 determines the On Demand Sls to berequested, the UE can request the On Demand Sls for SIM1 via SIM2 whileSIM2 is in the RRC Connected state. In various aspects, the amount oftime MO-data is buffered can be limited, and in some aspects can dependon the priority of the MO-data.

In other scenarios, SIM2 can be in the RRC Connected state. Again,depending on the specific scenario, SIM1 can be in RRC idle state anddetermining the On Demand SI(s) to be requested or SIM1 can be in themiddle of an ACQ procedure wherein SIM would figure out the On DemandSI(s) to be requested. In either type of scenario, once SIM1 determinesthe On Demand SIs to be requested, the UE can request the On Demand SIsfor SIM1 via SIM2 while SIM2 is in the RRC Connected state.

In further scenarios, SIM2 can be in RRC Connected state and the fastdormancy timer of SIM2 can be running, such that SIM2 is near the end ofits RRC Connected state. Again, depending on the specific scenario, SIM1can be in RRC idle state and determining the On Demand SI(s) to berequested or SIM1 can be in the middle of an ACQ procedure wherein SIMwould figure out the On Demand SI(s) to be requested. In either type ofscenario, SIM2 can buffer the initiated RRC Fast dormancy procedure,such that once SIM1 determines the On Demand SIs to be requested, the UEcan request the On Demand SIs for SIM1 via SIM2 while SIM2 is in the RRCConnected state, and can then perform RRC Connection release for SIM2due to forced Dormancy.

Referring to FIG. 5 , illustrated is a flow diagram of an example methodor process 500 employable at a UE that facilitates reducing RACHrequests from a first SIM without an established RRC connection of a UEin DSDS mode, according to various aspects discussed herein. In otheraspects, a machine readable medium can store instructions associatedwith method 500 that, when executed, can cause a UE (e.g., employingsystem 400 _(UE)) to perform the acts of method 500.

At 510, a UE can determine, via a first SIM (without an established RRCconnection) of the UE, at least one On Demand SI to be requested for thefirst SIM.

At 520, optionally, a UE can transition a second SIM (with anestablished RRC connection) to an RRC Connected state or delaytransition of the second SIM out of the RRC Connected state.

At 530, the UE can request the at least one On Demand SI via the secondSIM while the second SIM is in the RRC Connected state.

Additionally or alternatively, method 500 can include one or more otheracts described herein in connection with various aspects of a UE and/orsystem 400 _(UE) and the first set of techniques.

Reducing RACH Procedures to Obtain on Demand SI(s)

A second set of techniques can reduce RACH requests for On Demand SI(s)in response to an RRC paging message indicating SI modification of theOn Demand SI(s). When a UE receives an RRC paging message indicating SIModification and the SI(s) being modified are On Demand SI(s), then,because the RRC message was a page for SI modification, all the devicesin the vicinity would have been paged for SI modification.

Accordingly, in aspects employing the second set of techniques, the UEcan back off initiating a RACH procedure for the On Demand SI(s) and caninstead monitor the physical broadcast channel (PBCH) for a givenduration (e.g., X symbols/slots/subframes/etc.) in an attempt to readthe On Demand SI(s), wherein the back off/monitoring duration can befixed (e.g., predefined, etc.) or random (e.g., based on a predefinedrange, etc.). If the UE cannot decode the On Demand SI(s) within thegiven duration then the UE can initiate the RACH procedure to obtain theOn Demand SI(s).

Referring to FIG. 6 , illustrated is a flow diagram of an example methodor process 700 employable at a UE that facilitates reducing RACHrequests to obtain On Demand SI(s) in response to a page for SImodification, according to various aspects discussed herein. In otheraspects, a machine readable medium can store instructions associatedwith method 600 that, when executed, can cause a UE (e.g., employingsystem 400 _(UE)) to perform the acts of method 600.

At 610, a UE can receive a paging message indicating SI modification ofat least one On Demand SI.

At 620, the UE can monitor a physical broadcast channel for a givenduration and attempt to decode the at least one On Demand SI.

At 630, optionally, if the at least one On Demand SI was notsuccessfully decoded during the given duration, the UE can initiate aRACH procedure to obtain the at least one On Demand SI.

Additionally or alternatively, method 600 can include one or more otheracts described herein in connection with various aspects of a UE and/orsystem 400 _(UE) and the second set of techniques.

Additional Examples

Examples herein can include subject matter such as a method, means forperforming acts or blocks of the method, at least one machine-readablemedium including executable instructions that, when performed by amachine (e.g., a processor (e.g., processor, etc.) with memory, anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA), or the like) cause the machine to perform acts of themethod or of an apparatus or system for concurrent communication usingmultiple communication technologies according to aspects and examplesdescribed.

Example 1 is a baseband processor comprising processing circuitryconfigured to: determine, via a first Subscriber Identity Module (SIM)of a UE, at least one On Demand System Information (SI) for the firstSIM, wherein the first SIM does not have an established Radio ResourceControl (RRC) connection; and generate a request for the at least one OnDemand SI via a second SIM in an RRC Connected state, wherein the firstSIM and the second SIM are both associated with a common carrier.

Example 2 comprises the subject matter of any variation(s) of any ofexample(s) 1, wherein the first SIM is in an RRC Idle State when the atleast one On Demand SI is determined for the first SIM.

Example 3 comprises the subject matter of any variation(s) of any ofexample(s) 1-2, wherein the first SIM is in an acquisition procedurewhen the at least one On Demand SI is determined for the first SIM.

Example 4 comprises the subject matter of any variation(s) of any ofexample(s) 1-3, wherein, when the second SIM is in an RRC Inactivestate, the processing circuitry is further configured to buffer an RRCresume procedure for Mobile Originated (MO)-Data for the second SIM fora given duration to enable the second SIM to generate the request forthe at least one On Demand SI via the second SIM in the RRC Connectedstate.

Example 5 comprises the subject matter of any variation(s) of any ofexample(s) 4, wherein the given duration is based at least in part on apriority of the MO-Data.

Example 6 comprises the subject matter of any variation(s) of any ofexample(s) 1-5, wherein the second SIM is configured to remain in theRRC Connected state throughout the determination of the at least one OnDemand SI for the first SIM.

Example 7 comprises the subject matter of any variation(s) of any ofexample(s) 6, wherein the processing circuitry is further configured tobuffer an initiated RRC Fast Dormancy procedure for the second SIM untilafter the request for the at least one On Demand SI is generated.

Example 8 comprises the subject matter of any variation(s) of any ofexample(s) 7, wherein, in response to obtaining the at least one OnDemand SI for the first SIM, the one or more processors are furtherconfigured to perform an RRC Connection release for the second SIM.

Example 9 is a baseband processor comprising processing circuitryconfigured to: process a Radio Resource Control (RRC) paging messagethat indicates a System Information (SI) Modification for at least oneOn Demand SI; monitor, in response to the RRC paging message, a PhysicalBroadcast Channel (PBCH) for a given duration; and attempt to decode theat least one On Demand SI from the PBCH during the given duration.

Example 10 comprises the subject matter of any variation(s) of any ofexample(s) 9, wherein the given duration is randomly determined.

Example 11 comprises the subject matter of any variation(s) of any ofexample(s) 9, wherein the given duration is fixed.

Example 12 comprises the subject matter of any variation(s) of any ofexample(s) 9, wherein, in response to the at least one On Demand SI notbeing successfully decoded during the given duration, the processingcircuitry is further configured to initiate a Random Access Channel(RACH) procedure to obtain the at least one On Demand SI.

Example 13 is a method, comprising: determining, via a first SubscriberIdentity Module (SIM) of the UE, at least one On Demand SystemInformation (SI) for the first SIM, wherein the first SIM does not havean established Radio Resource Control (RRC) connection; and generating arequest for the at least one On Demand SI via a second SIM in an RRCConnected state, wherein the first SIM and the second SIM are bothassociated with a common carrier.

Example 14 comprises the subject matter of any variation(s) of any ofexample(s) 13, wherein the first SIM is in an RRC Idle when the at leastone On Demand SI is determined for the first SIM.

Example 15 comprises the subject matter of any variation(s) of any ofexample(s) 13-14, wherein the first SIM is in an acquisition procedurewhen the at least one On Demand SI is determined for the first SIM.

Example 16 comprises the subject matter of any variation(s) of any ofexample(s) 13-15, further comprising, when the second SIM is in an RRCInactive state, buffering an RRC resume procedure for Mobile Originated(MO)-Data for the second SIM for a given duration to enable the secondSIM to generate the request for the at least one On Demand SI via thesecond SIM in the RRC Connected state.

Example 17 comprises the subject matter of any variation(s) of any ofexample(s) 16, wherein the given duration is based at least in part on apriority of the MO-Data.

Example 18 comprises the subject matter of any variation(s) of any ofexample(s) 13-17, wherein the second SIM is configured to remain in theRRC connected state throughout the determination of the at least one OnDemand SI for the first SIM.

Example 19 comprises the subject matter of any variation(s) of any ofexample(s) 18, further comprising buffering an initiated RRC FastDormancy procedure for the second SIM until after the request for the atleast one On Demand SI is generated.

Example 20 comprises the subject matter of any variation(s) of any ofexample(s) 19, further comprising, in response to obtaining the at leastone On Demand SI for the first SIM, performing an RRC Connection releasefor the second SIM.

Example 21 is a method, comprising: processing a Radio Resource Control(RRC) paging message that indicates a System Information (SI)Modification for at least one On Demand SI; monitoring, in response tothe RRC paging message, a Physical Broadcast Channel (PBCH) for a givenduration; and attempting to decode the at least one On Demand SI fromthe PBCH during the given duration.

Example 22 comprises the subject matter of any variation(s) of any ofexample(s) 21, wherein the given duration is randomly determined.

Example 23 comprises the subject matter of any variation(s) of any ofexample(s) 21, wherein the given duration is fixed.

Example 24 comprises the subject matter of any variation(s) of any ofexample(s) 21-23, further comprising, in response to the at least one OnDemand SI not being successfully decoded during the given duration,initiating a Random Access Channel (RACH) procedure to obtain the atleast one On Demand SI.

Example 25 is a User Equipment (UE), comprising: first and secondSubscriber Identity Modules (SIMs); and one or more processorsconfigured to: determine, via the first SIM, at least one On DemandSystem Information (SI) for the first SIM, wherein the first SIM doesnot have an established Radio Resource Control (RRC) connection; andgenerate a request for the at least one On Demand SI via the second SIMin an RRC Connected state, wherein the first SIM and the second SIM areboth associated with a common carrier.

Example 26 comprises the subject matter of any variation(s) of any ofexample(s) 25, wherein the first SIM is in an RRC Idle state when the atleast one On Demand SI is determined for the first SIM.

Example 27 comprises the subject matter of any variation(s) of any ofexample(s) 25-26, wherein the first SIM is in an acquisition procedurewhen the at least one On Demand SI is determined for the first SIM.

Example 28 comprises the subject matter of any variation(s) of any ofexample(s) 25-27, wherein, when the second SIM is in an RRC Inactivestate, the one or more processors are further configured to buffer anRRC resume procedure for Mobile Originated (MO)-Data for the second SIMfor a given duration to enable the second SIM to generate the requestfor the at least one On Demand SI via the second SIM in the RRCConnected state.

Example 29 comprises the subject matter of any variation(s) of any ofexample(s) 28, wherein the given duration is based at least in part on apriority of the MO-Data.

Example 30 comprises the subject matter of any variation(s) of any ofexample(s) 25-29, wherein the second SIM is configured to remain in theRRC Connected state throughout the determination of the at least one OnDemand SI for the first SIM.

Example 31 comprises the subject matter of any variation(s) of any ofexample(s) 30, wherein the one or more processors are further configuredto buffer an initiated RRC Fast Dormancy procedure for the second SIMuntil after the request for the at least one On Demand SI is generated.

Example 32 comprises the subject matter of any variation(s) of any ofexample(s) 31, wherein, in response to obtaining the at least one OnDemand SI for the first SIM, the one or more processors are furtherconfigured to perform an RRC Connection release for the second SIM.

Example 33 is a User Equipment (UE), comprising: one or more processorsconfigured to: process a Radio Resource Control (RRC) paging messagethat indicates a System Information (SI) Modification for at least oneOn Demand SI; monitor, in response to the RRC paging message, a PhysicalBroadcast Channel (PBCH) for a given duration; and attempt to decode theat least one SI from the PBCH during the given duration.

Example 34 comprises the subject matter of any variation(s) of any ofexample(s) 33, wherein the given duration is randomly determined.

Example 35 comprises the subject matter of any variation(s) of any ofexample(s) 33, wherein the given duration is fixed.

Example 36 comprises the subject matter of any variation(s) of any ofexample(s) 33-25, wherein, in response to the at least one On Demand SInot being successfully decoded during the given duration, the one ormore processors are further configured to initiate a Random AccessChannel (RACH) procedure to obtain the at least one On Demand SI.

Example 37 comprises an apparatus comprising means for executing any ofthe described operations of examples 1-36.

Example 38 comprises a machine readable medium that stores instructionsfor execution by a processor to perform any of the described operationsof examples 1-36.

Example 39 comprises an apparatus comprising: a memory interface; andprocessing circuitry configured to: perform any of the describedoperations of examples 1-36.

Example 40 comprises a User Equipment (UE) configured to execute any ofthe described operations of examples 1-36.

The above description of illustrated aspects of the subject disclosure,including what is described in the Abstract, is not intended to beexhaustive or to limit the disclosed aspects to the precise formsdisclosed. While specific aspects and examples are described herein forillustrative purposes, various modifications are possible that areconsidered within the scope of such aspects and examples, as thoseskilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various aspects and corresponding Figures, whereapplicable, it is to be understood that other similar aspects can beused or modifications and additions can be made to the described aspectsfor performing the same, similar, alternative, or substitute function ofthe disclosed subject matter without deviating therefrom. Therefore, thedisclosed subject matter should not be limited to any single aspectdescribed herein, but rather should be construed in breadth and scope inaccordance with the appended claims below.

In particular regard to the various functions performed by the abovedescribed components or structures (assemblies, devices, circuits,systems, etc.), the terms (including a reference to a “means”) used todescribe such components are intended to correspond, unless otherwiseindicated, to any component or structure which performs the specifiedfunction of the described component (e.g., that is functionallyequivalent), even though not structurally equivalent to the disclosedstructure which performs the function in the herein illustratedexemplary implementations. In addition, while a particular feature mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application.

What is claimed is:
 1. A baseband processor comprising processingcircuitry configured to: determine, via a first Subscriber IdentityModule (SIM) of a User Equipment (UE), at least one On Demand SystemInformation (SI) to be requested for the first SIM, wherein the firstSIM does not have an established Radio Resource Control (RRC)connection; and in response to determining the at least one On Demand SIto be requested for the first SIM, generate a request for the at leastone On Demand SI via a second SIM in an RRC Connected state, wherein thefirst SIM and the second SIM are both associated with a common carrier.2. The baseband processor of claim 1, wherein the first SIM is in an RRCIdle State when the at least one On Demand SI is determined for thefirst SIM.
 3. The baseband processor of claim 1, wherein the first SIMis in an acquisition procedure when the at least one On Demand SI isdetermined for the first SIM.
 4. The baseband processor of claim 1,wherein, when the second SIM is in an RRC Inactive state, the processingcircuitry is further configured to buffer an RRC resume procedure forMobile Originated (MO)-Data for the second SIM for a given duration toenable the second SIM to generate the request for the at least one OnDemand SI via the second SIM in the RRC Connected state.
 5. The basebandprocessor of claim 4, wherein the given duration is based at least inpart on a priority of the MO-Data.
 6. The baseband processor of claim 1,wherein the second SIM is configured to remain in the RRC Connectedstate throughout the determination of the at least one On Demand SI forthe first SIM.
 7. The baseband processor of claim 6, wherein theprocessing circuitry is further configured to buffer an initiated RRCFast Dormancy procedure for the second SIM until after the request forthe at least one On Demand SI is generated.
 8. The baseband processor ofclaim 7, wherein, in response to obtaining the at least one On Demand SIfor the first SIM, the processing circuitry is further configured toperform an RRC Connection release for the second SIM.
 9. A UserEquipment (UE), comprising: first and second Subscriber Identity Modules(SIMs); and one or more processors configured to: determine, via thefirst SIM, at least one On Demand System Information (SI) to berequested for the first SIM, wherein the first SIM does not have anestablished Radio Resource Control (RRC) connection; and in response todetermining the at least one On Demand SI to be requested for the firstSIM, generate a request for the at least one On Demand SI via the secondSIM in an RRC Connected state, wherein the first SIM and the second SIMare both associated with a common carrier.
 10. The UE of claim 9,wherein the first SIM is in an RRC Idle state when the at least one OnDemand SI is determined for the first SIM.
 11. The UE of claim 9,wherein the first SIM is in an acquisition procedure when the at leastone On Demand SI is determined for the first SIM.
 12. The UE of claim 9,wherein, when the second SIM is in an RRC Inactive state, the one ormore processors are further configured to buffer an RRC resume procedurefor Mobile Originated (MO)-Data for the second SIM for a given durationto enable the second SIM to generate the request for the at least one OnDemand SI via the second SIM in the RRC Connected state.
 13. The UE ofclaim 12, wherein the given duration is based at least in part on apriority of the MO-Data.
 14. The UE of claim 9, wherein the second SIMis configured to remain in the RRC Connected state throughout thedetermination of the at least one On Demand SI for the first SIM. 15.The UE of claim 14, wherein the one or more processors are furtherconfigured to buffer an initiated RRC Fast Dormancy procedure for thesecond SIM until after the request for the at least one On Demand SI isgenerated.
 16. The UE of claim 15, wherein, in response to obtaining theat least one On Demand SI for the first SIM, the one or more processorsare further configured to perform an RRC Connection release for thesecond SIM.
 17. A method, comprising: determining, via a firstSubscriber Identity Module (SIM) of a User Equipment (UE), at least oneOn Demand System Information (SI) to be requested for the first SIM,wherein the first SIM does not have an established Radio ResourceControl (RRC); and in response to determining the at least one On DemandSI to be requested for the first SIM, generating a request for the atleast one On Demand SI via a second SIM of the UE, the second SIM in aRRC Connected state, wherein the first SIM and the second SIM are bothassociated with a common carrier.
 18. The method of claim 17, whereinthe first SIM is in an RRC Idle state when the at least one On Demand SIis determined for the first SIM.
 19. The method of claim 17, wherein thefirst SIM is in an acquisition procedure when the at least one On DemandSI is determined for the first SIM.
 20. The method of claim 17, furthercomprising, when the second SIM is in an RRC Inactive state, bufferingan RRC resume procedure for Mobile Originated (MO)-Data for the secondSIM for a given duration to enable the second SIM to generate therequest for the at least one On Demand SI via the second SIM in the RRCConnected state.